-
Notifications
You must be signed in to change notification settings - Fork 13.4k
Remove eval_always for lib_features. #91330
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
@bors try @rust-timer queue |
Awaiting bors try build completion. @rustbot label: +S-waiting-on-perf |
⌛ Trying commit 877b2d7 with merge 49fd54458898c27659727aca3e321a6a4296a642... |
☀️ Try build successful - checks-actions |
Queued 49fd54458898c27659727aca3e321a6a4296a642 with parent db9d361, future comparison URL. |
Finished benchmarking commit (49fd54458898c27659727aca3e321a6a4296a642): comparison url. Summary: This benchmark run did not return any relevant changes. If you disagree with this performance assessment, please file an issue in rust-lang/rustc-perf. Benchmarking this pull request likely means that it is perf-sensitive, so we're automatically marking it as not fit for rolling up. While you can manually mark this PR as fit for rollup, we strongly recommend not doing so since this PR led to changes in compiler perf. @bors rollup=never |
@bors r+ |
📌 Commit 877b2d7 has been approved by |
☀️ Test successful - checks-actions |
Finished benchmarking commit (90912e6): comparison url. Summary: This benchmark run did not return any relevant changes. If you disagree with this performance assessment, please file an issue in rust-lang/rustc-perf. @rustbot label: -perf-regression |
r? @Aaron1011